Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference
475-tree-1
name
1662
tree-preservation-order

undefined

475-tpo-1
uprn
address-text
point
POINT (-1.023616 50.882517)
geometry
MULTIPOLYGON (((-1.023503 50.882505,-1.023508 50.882527,-1.023524 50.882548,-1.023548 50.882564,-1.023580 50.882574,-1.023615 50.882578,-1.023650 50.882575,-1.023682 50.882565,-1.023707 50.882549,-1.023724 50.882529,-1.023730 50.882507,-1.023725 50.882485,-1.023709 50.882465,-1.023684 50.882448,-1.023653 50.882438,-1.023618 50.882434,-1.023583 50.882437,-1.023551 50.882447,-1.023525 50.882463,-1.023509 50.882483,-1.023503 50.882505)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL